SD- Deepak- Damodhier- 2016-07-18 - 27637 - Spec - Online Return creation for Menlo (Rizwan by 2015-08-05) #salesorders #ABAP #ABAPPending #OrderEntry

SPECIFICATIONS

27637 -Spec- Online Return creation for Menlo


Purpose


Create return order with reference to invoice and auto return delivery

Admin Info


Purpose
Create return order with reference to invoice and auto return delivery
Requested By
Rizwan Shah
Spec Created By
Deepak Yasam
Spec Created Date
07/18/2016
Spec QA by
Surya Basa
Objects
BAPI_CUSTOMERRETURN_CREATE
/AFS/BAPI_SALESORD_CHANGE
BAPI_OUTB_DELIVERY_CREATE_SLS
ZRE_MENLO_CREATE
Document Status
WIP


Estimates



Sl.No
Activity
Estimation in Hours
New Change estimate
1
Research
24
00
2
Documentation
06
02
3
Development/ Config
60
12
4
Unit test in DEV
20
04
5
Unit test in QUA
00
00
6
Other activity
00
00

TOTAL
74
18

References


Prior Tickets

[Provide links of prior associated Spec / Break Fix BOSS document(s)]

None


Documents

[Attach any document(s) received for the requirement(s)]

None


Spec Changes


[List the changes made to program after the approval of the original requirement along with the Date on which the change request was received and the name of the initiator]

Sl.
Change Details
Requested By
Requested On
Notes if any
1
The layout needs to be changed
Rizwan Shah
09/19/2016
NA




















Functional Requirement


Purpose/WHY:

[Explain the purpose of the project and the reason why this requirement has come]

Business tried to create Winshuttle for the Menlo DC in Ersel to allow them to create a returns order with reference when web product comes back to the wearhouse. This was not been successful and want to develop a transaction for them to be able to do this in SAP.

The user will have a screen where they can enter the delivery number, UPC and QTY.

The program should then go look up the Invoice from that delivery number. Create a returns order w/ reference to the billing document, and only use the lines with relevant UPC’s and QTY entered on the transaction screen.

The returns order should then auto create the delivery to drop it to the DC.

In Scope:

[List the activities to be included in scope]
Only the return order(ZRE) and corresponding return delivery with reference to billing document is created through transaction.

Out of Scope:

[Out of scope activities]
No other order types are created.

Solution Summary


[Discuss this section with Requester and get approval prior to beginning work]

BAPI's :
For Return sales order creation , BAPI_CUSTOMERRETURN_CREATE should be used that is not specific to AFS.
For Return sales order changes to delete unwanted UPC's and Qty's , /AFS/BAPI_SALESORD_CHANGE is used that is AFS Specific.
As one AFS Non specific BAPI is used ,any unforeseen issues in NEP can be observed.
For return delivery creation ,BAPI_OUTB_DELIVERY_CREATE_SLS should be used.

Ex - 60001523

Functionality of the transaction:
1. A new transaction ZRET should be created with the below inputs.
Delivery number - single entry in the selection screen
EAN/UPC - Single /Multiple entries in the selection screen
Quantity - Single/Multple entries in the selection screen
2. The custom program should fetch the corresponding invoice number for the respective delivery,UPC in the selection screen and a return order should be created for the desired UPC and quantity alone.
3.Once the return order is created , the program should create a return delivery.

Layout changes:
1. The Delivery input should be added at the top
2. The order reason should be added at the top
3.The billing block should be removed in the return order.
4. The text should be changed to Please provide Single Delivery details to create return order.


Layout change.jpg

Test Plan

[List test scenarios/cases to be executed here]

With Single UPC/EAN and Quantity:

Test ID
Test Scenario
Expected Result
SD-001
Input below values in the t.code
Del number - Valid
EAN/UPC - Valid
Quantity - Valid
The return Order and return delivery should be created for the input UPC and Qty
SD-002
Input below values in the t.code
Del number - Valid
EAN/UPC - InValid
Quantity - Valid
An error log should be displayed as 'Please check the input'
SD-003
Input below values in the t.code
Del number - InValid
EAN/UPC - Valid
Quantity - Valid
An error log should be displayed as 'Please check the input'
SD-005
Input below values in the t.code
Del number - Valid
EAN/UPC - Valid
Quantity - Valid and over referenced
An error log should be displayed Return quantiity is more than available qunatity'

With Mutiple UPC/EAN's and Quantities:

Test ID
Test Scenario
Expected Result
SD-001
Input below values in the t.code
Del number - Valid
EAN/UPC - Valid
Quantity - Valid
The return Order and return delivery should be created for the input UPC's and Qty's
SD-002
Input below values in the t.code
Del number - Valid
EAN/UPC - InValid UPC's
Quantity - Valid
An error log should be displayed as 'Please check input'
SD-003
Input below values in the t.code
Del number - InValid
EAN/UPC - Valid
Quantity - Valid
An error log should be displayed as 'Please check input'
SD-004
Input below values in the t.code
Del number - Valid
EAN/UPC - InValid and Valid UPC's
Quantity - Valid
An error log should be displayed as 'Please check input'
SD-005
Input below values in the t.code
Del number - Valid
EAN/UPC - Valid
Quantity - Valid and over referenced

(no single return order is created for the UPC)
An error log should be displayed 'Return Order quantity is more than the invoice quantity'
SD-006
Input below values in the t.code
Del number - Valid
EAN/UPC - Valid
Quantity - Valid and over referenced

(Return orders already exists for the UPC)
An error log should be displayed 'Return Order quantity is more than the available quantity'
SD-007
Input below values in the t.code
Del number - Valid
EAN/UPC - Valid(same UPC)
Quantity - Valid
The second UPC entry should be deleted and the return SO and return delivery should be created.
SD-008
Input below values in the t.code
Del number - Valid(More than one delivery)
EAN/UPC - Valid
Quantity - Valid
A log should be displayed 'Please enter only one delivery details'

Solution Details


[Provide complete technical details for configuration or programming here]

Will update the details as soon as development is completed.


Issues


[List Issues / Bugs identified in configuration or development]

None